Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): Bump similar-asserts from 1.5.0 to 1.6.0 #21222

Merged
merged 1 commit into from
Oct 1, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 6, 2024

Bumps similar-asserts from 1.5.0 to 1.6.0.

Changelog

Sourced from similar-asserts's changelog.

1.6.0

  • Loosen static lifetime bounds for labels. #9
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot requested a review from a team as a code owner September 6, 2024 04:20
@dependabot dependabot bot added domain: deps Anything related to Vector's dependencies no-changelog Changes in this PR do not need user-facing explanations in the release changelog labels Sep 6, 2024
@github-actions github-actions bot added the domain: core Anything related to core crates i.e. vector-core, core-common, etc label Sep 6, 2024
@jszwedko jszwedko added this pull request to the merge queue Sep 7, 2024
Copy link

github-actions bot commented Sep 7, 2024

Regression Detector Results

Run ID: ba12b309-d778-408d-b855-029c9725413b Metrics dashboard

Baseline: 00ef42b
Comparison: a1123c0

Performance changes are noted in the perf column of each table:

  • ✅ = significantly better comparison variant performance
  • ❌ = significantly worse comparison variant performance
  • ➖ = no significant change in performance

Significant changes in experiment optimization goals

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

perf experiment goal Δ mean % Δ mean % CI links
syslog_regex_logs2metric_ddmetrics ingress throughput -5.49 [-5.66, -5.32]

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf experiment goal Δ mean % Δ mean % CI links
file_to_blackhole egress throughput +1.17 [-5.81, +8.16]

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI links
syslog_log2metric_humio_metrics ingress throughput +2.08 [+1.91, +2.24]
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +1.81 [+1.71, +1.90]
file_to_blackhole egress throughput +1.17 [-5.81, +8.16]
otlp_http_to_blackhole ingress throughput +0.88 [+0.76, +1.01]
datadog_agent_remap_datadog_logs ingress throughput +0.59 [+0.41, +0.77]
http_to_s3 ingress throughput +0.50 [+0.24, +0.77]
http_to_http_acks ingress throughput +0.28 [-0.99, +1.54]
http_to_http_noack ingress throughput +0.17 [+0.09, +0.26]
otlp_grpc_to_blackhole ingress throughput +0.09 [-0.02, +0.20]
http_to_http_json ingress throughput +0.04 [-0.01, +0.09]
datadog_agent_remap_blackhole_acks ingress throughput +0.03 [-0.08, +0.14]
splunk_hec_to_splunk_hec_logs_noack ingress throughput +0.02 [-0.08, +0.11]
splunk_hec_indexer_ack_blackhole ingress throughput +0.01 [-0.06, +0.09]
splunk_hec_to_splunk_hec_logs_acks ingress throughput +0.00 [-0.11, +0.11]
http_text_to_http_json ingress throughput -0.03 [-0.15, +0.10]
syslog_humio_logs ingress throughput -0.04 [-0.17, +0.08]
socket_to_socket_blackhole ingress throughput -0.15 [-0.21, -0.09]
fluent_elasticsearch ingress throughput -0.20 [-0.69, +0.28]
http_elasticsearch ingress throughput -0.33 [-0.51, -0.14]
datadog_agent_remap_datadog_logs_acks ingress throughput -0.38 [-0.50, -0.26]
syslog_splunk_hec_logs ingress throughput -0.65 [-0.74, -0.56]
datadog_agent_remap_blackhole ingress throughput -0.86 [-0.96, -0.76]
syslog_log2metric_splunk_hec_metrics ingress throughput -0.91 [-1.01, -0.81]
splunk_hec_route_s3 ingress throughput -1.78 [-2.10, -1.46]
syslog_loki ingress throughput -2.12 [-2.22, -2.02]
syslog_regex_logs2metric_ddmetrics ingress throughput -5.49 [-5.66, -5.32]

Explanation

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

  3. Its configuration does not mark it "erratic".

@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Sep 7, 2024
@jszwedko jszwedko added this pull request to the merge queue Sep 24, 2024
@jszwedko jszwedko removed this pull request from the merge queue due to the queue being cleared Sep 24, 2024
@dependabot dependabot bot force-pushed the dependabot/cargo/similar-asserts-1.6.0 branch from 22f3b78 to 327b39c Compare September 27, 2024 23:53
Bumps [similar-asserts](https://github.com/mitsuhiko/similar-asserts) from 1.5.0 to 1.6.0.
- [Changelog](https://github.com/mitsuhiko/similar-asserts/blob/main/CHANGELOG.md)
- [Commits](mitsuhiko/similar-asserts@1.5.0...1.6.0)

---
updated-dependencies:
- dependency-name: similar-asserts
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/cargo/similar-asserts-1.6.0 branch from 327b39c to 70a4dce Compare September 30, 2024 21:34
@jszwedko jszwedko added this pull request to the merge queue Oct 1, 2024
Copy link

github-actions bot commented Oct 1, 2024

Regression Detector Results

Run ID: 215c98bc-8f69-47b9-9745-b14dab2916d5 Metrics dashboard

Baseline: d06212d
Comparison: 6ef3d5e

Performance changes are noted in the perf column of each table:

  • ✅ = significantly better comparison variant performance
  • ❌ = significantly worse comparison variant performance
  • ➖ = no significant change in performance

Significant changes in experiment optimization goals

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

perf experiment goal Δ mean % Δ mean % CI links
splunk_hec_route_s3 ingress throughput +6.27 [+5.90, +6.64]

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf experiment goal Δ mean % Δ mean % CI links
file_to_blackhole egress throughput -2.36 [-9.39, +4.67]

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI links
splunk_hec_route_s3 ingress throughput +6.27 [+5.90, +6.64]
socket_to_socket_blackhole ingress throughput +2.85 [+2.67, +3.02]
syslog_log2metric_splunk_hec_metrics ingress throughput +2.23 [+2.11, +2.34]
fluent_elasticsearch ingress throughput +1.62 [+1.13, +2.12]
http_text_to_http_json ingress throughput +1.37 [+1.25, +1.50]
datadog_agent_remap_blackhole_acks ingress throughput +1.16 [+1.03, +1.30]
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +0.85 [+0.75, +0.94]
datadog_agent_remap_datadog_logs ingress throughput +0.68 [+0.47, +0.89]
syslog_log2metric_humio_metrics ingress throughput +0.20 [+0.08, +0.33]
datadog_agent_remap_datadog_logs_acks ingress throughput +0.16 [-0.02, +0.33]
http_elasticsearch ingress throughput +0.05 [-0.12, +0.22]
http_to_http_json ingress throughput +0.01 [-0.03, +0.05]
syslog_humio_logs ingress throughput +0.01 [-0.13, +0.14]
splunk_hec_to_splunk_hec_logs_noack ingress throughput +0.01 [-0.09, +0.10]
splunk_hec_to_splunk_hec_logs_acks ingress throughput +0.00 [-0.10, +0.10]
http_to_http_noack ingress throughput +0.00 [-0.02, +0.02]
otlp_grpc_to_blackhole ingress throughput -0.00 [-0.13, +0.12]
splunk_hec_indexer_ack_blackhole ingress throughput -0.03 [-0.11, +0.05]
datadog_agent_remap_blackhole ingress throughput -0.21 [-0.35, -0.08]
http_to_s3 ingress throughput -0.49 [-0.77, -0.22]
syslog_regex_logs2metric_ddmetrics ingress throughput -0.74 [-0.88, -0.60]
syslog_splunk_hec_logs ingress throughput -0.85 [-0.95, -0.76]
syslog_loki ingress throughput -0.88 [-0.96, -0.80]
http_to_http_acks ingress throughput -1.57 [-2.80, -0.34]
otlp_http_to_blackhole ingress throughput -1.99 [-2.22, -1.76]
file_to_blackhole egress throughput -2.36 [-9.39, +4.67]

Explanation

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

  3. Its configuration does not mark it "erratic".

Copy link

github-actions bot commented Oct 1, 2024

Regression Detector Results

Run ID: 2a2b83f9-53ef-48a2-9d9c-104fd69a59b6 Metrics dashboard

Baseline: 4d62905
Comparison: efde59a

Performance changes are noted in the perf column of each table:

  • ✅ = significantly better comparison variant performance
  • ❌ = significantly worse comparison variant performance
  • ➖ = no significant change in performance

No significant changes in experiment optimization goals

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf experiment goal Δ mean % Δ mean % CI links
file_to_blackhole egress throughput +5.47 [-1.84, +12.79]

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI links
file_to_blackhole egress throughput +5.47 [-1.84, +12.79]
datadog_agent_remap_blackhole_acks ingress throughput +4.06 [+3.90, +4.22]
syslog_log2metric_splunk_hec_metrics ingress throughput +2.31 [+2.20, +2.43]
otlp_http_to_blackhole ingress throughput +1.95 [+1.81, +2.08]
fluent_elasticsearch ingress throughput +1.62 [+1.13, +2.11]
otlp_grpc_to_blackhole ingress throughput +0.68 [+0.57, +0.79]
socket_to_socket_blackhole ingress throughput +0.61 [+0.51, +0.71]
datadog_agent_remap_datadog_logs_acks ingress throughput +0.27 [+0.07, +0.47]
http_to_http_noack ingress throughput +0.14 [+0.06, +0.21]
splunk_hec_indexer_ack_blackhole ingress throughput +0.01 [-0.07, +0.10]
http_elasticsearch ingress throughput +0.01 [-0.17, +0.19]
http_to_s3 ingress throughput +0.01 [-0.28, +0.29]
splunk_hec_to_splunk_hec_logs_noack ingress throughput +0.00 [-0.09, +0.10]
splunk_hec_to_splunk_hec_logs_acks ingress throughput -0.00 [-0.11, +0.10]
http_to_http_json ingress throughput -0.00 [-0.03, +0.02]
syslog_log2metric_humio_metrics ingress throughput -0.30 [-0.43, -0.17]
syslog_humio_logs ingress throughput -0.31 [-0.47, -0.16]
syslog_regex_logs2metric_ddmetrics ingress throughput -0.55 [-0.72, -0.39]
splunk_hec_route_s3 ingress throughput -0.66 [-0.97, -0.34]
datadog_agent_remap_blackhole ingress throughput -0.66 [-0.78, -0.54]
syslog_loki ingress throughput -1.03 [-1.13, -0.94]
http_text_to_http_json ingress throughput -1.07 [-1.20, -0.94]
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput -1.19 [-1.29, -1.08]
datadog_agent_remap_datadog_logs ingress throughput -1.33 [-1.54, -1.12]
http_to_http_acks ingress throughput -1.43 [-2.64, -0.22]
syslog_splunk_hec_logs ingress throughput -2.30 [-2.46, -2.14]

Explanation

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

  3. Its configuration does not mark it "erratic".

Copy link

github-actions bot commented Oct 1, 2024

Regression Detector Results

Run ID: 87d6d8e4-3cde-4e27-80ef-0ee8e8ee37d4 Metrics dashboard

Baseline: 145bf0a
Comparison: 6b77508

Performance changes are noted in the perf column of each table:

  • ✅ = significantly better comparison variant performance
  • ❌ = significantly worse comparison variant performance
  • ➖ = no significant change in performance

Significant changes in experiment optimization goals

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

perf experiment goal Δ mean % Δ mean % CI links
http_text_to_http_json ingress throughput +5.17 [+4.84, +5.50]

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf experiment goal Δ mean % Δ mean % CI links
file_to_blackhole egress throughput +11.14 [+3.91, +18.37]

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI links
file_to_blackhole egress throughput +11.14 [+3.91, +18.37]
http_text_to_http_json ingress throughput +5.17 [+4.84, +5.50]
syslog_log2metric_humio_metrics ingress throughput +3.26 [+3.15, +3.36]
http_to_http_acks ingress throughput +0.92 [-0.31, +2.15]
datadog_agent_remap_blackhole ingress throughput +0.75 [+0.65, +0.86]
socket_to_socket_blackhole ingress throughput +0.64 [+0.57, +0.71]
syslog_splunk_hec_logs ingress throughput +0.54 [+0.42, +0.67]
syslog_loki ingress throughput +0.48 [+0.40, +0.57]
syslog_log2metric_splunk_hec_metrics ingress throughput +0.34 [+0.24, +0.45]
datadog_agent_remap_blackhole_acks ingress throughput +0.24 [+0.10, +0.38]
http_to_http_noack ingress throughput +0.11 [+0.04, +0.17]
http_to_http_json ingress throughput +0.07 [+0.01, +0.12]
splunk_hec_to_splunk_hec_logs_noack ingress throughput +0.00 [-0.09, +0.09]
splunk_hec_to_splunk_hec_logs_acks ingress throughput +0.00 [-0.12, +0.12]
splunk_hec_indexer_ack_blackhole ingress throughput -0.00 [-0.09, +0.08]
fluent_elasticsearch ingress throughput -0.02 [-0.51, +0.48]
otlp_grpc_to_blackhole ingress throughput -0.04 [-0.15, +0.07]
http_to_s3 ingress throughput -0.20 [-0.47, +0.07]
splunk_hec_route_s3 ingress throughput -0.25 [-0.56, +0.06]
http_elasticsearch ingress throughput -0.26 [-0.44, -0.09]
syslog_humio_logs ingress throughput -0.83 [-0.95, -0.72]
datadog_agent_remap_datadog_logs_acks ingress throughput -0.89 [-1.07, -0.71]
otlp_http_to_blackhole ingress throughput -1.28 [-1.39, -1.16]
datadog_agent_remap_datadog_logs ingress throughput -2.74 [-2.98, -2.50]
syslog_regex_logs2metric_ddmetrics ingress throughput -3.02 [-3.15, -2.89]
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput -3.49 [-3.63, -3.34]

Explanation

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

  3. Its configuration does not mark it "erratic".

Merged via the queue into master with commit 6b77508 Oct 1, 2024
50 checks passed
@jszwedko jszwedko deleted the dependabot/cargo/similar-asserts-1.6.0 branch October 1, 2024 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain: core Anything related to core crates i.e. vector-core, core-common, etc domain: deps Anything related to Vector's dependencies no-changelog Changes in this PR do not need user-facing explanations in the release changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant